FEATURE: Auto assign new assets to default collection and prevent removing last collection depending on config #251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sebobo
force-pushed
the
feature/auto-assign-assets-to-default-collections
branch
3 times, most recently
from
1cb6ce4
to
e241be7
Compare
This feature existed for default media browser but not for the Media.UI so far
Sebobo
force-pushed
the
feature/auto-assign-assets-to-default-collections
branch
from
e241be7
to
25595cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The old media browser auto assigned assets without a collection to the default collection of a site if one is configured. This behaviour has now been duplicated.
Also It's now impossible to remove the last collection of an asset in "folder mode" and when a default collection is configured for the current site.
Resolves: #246
Based on: #245